Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: bd6e020d82f4618c25e4c67958e311e3d9e06231fad290235e66c242b277fe31

Tx prefix hash: ab1274e3b9080d2f3ce2b8215900a22ca274e3b4b77567294816ca01d9eb0871
Tx public key: 4c31ebd8e892c725a098cfac2cda99a18caadce94558f49b09ea23183b0760e7
Timestamp: 1755175459 Timestamp [UCT]: 2025-08-14 12:44:19 Age [y:d:h:m:s]: 00:007:06:29:05
Block: 1346663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4810 RingCT/type: yes/0
Extra: 014c31ebd8e892c725a098cfac2cda99a18caadce94558f49b09ea23183b0760e70211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08e35da4a36853b00a24d424712c1840aa754d0e0e9fda989fcc79fd410efc2d 0.600000000000 1834564 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1346673, "vin": [ { "gen": { "height": 1346663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08e35da4a36853b00a24d424712c1840aa754d0e0e9fda989fcc79fd410efc2d" } } ], "extra": [ 1, 76, 49, 235, 216, 232, 146, 199, 37, 160, 152, 207, 172, 44, 218, 153, 161, 140, 170, 220, 233, 69, 88, 244, 155, 9, 234, 35, 24, 59, 7, 96, 231, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8