Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb9c9a30b80321efe4c2097a6402aade82102e46043b3cbb7c15eddf02c0aaf5

Tx prefix hash: 9b568e18c71c8ad70def0c249ef0434f76e5447a8309d7509e392465f2ff38ba
Tx public key: 824a1fcb3a571faea37ca359380cb8fdaf1d3e150bdf3167128b04c22dbefc51
Timestamp: 1728020631 Timestamp [UCT]: 2024-10-04 05:43:51 Age [y:d:h:m:s]: 00:188:19:34:51
Block: 1124054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134742 RingCT/type: yes/0
Extra: 01824a1fcb3a571faea37ca359380cb8fdaf1d3e150bdf3167128b04c22dbefc51021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e3cd2cbaacefcba9c4da11b7e5f765b100fd4ad80f5360e91aa0c7a7b80988a 0.600000000000 1606617 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": 1124064, "vin": [ { "gen": { "height": 1124054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e3cd2cbaacefcba9c4da11b7e5f765b100fd4ad80f5360e91aa0c7a7b80988a" } } ], "extra": [ 1, 130, 74, 31, 203, 58, 87, 31, 174, 163, 124, 163, 89, 56, 12, 184, 253, 175, 29, 62, 21, 11, 223, 49, 103, 18, 139, 4, 194, 45, 190, 252, 81, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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