Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d300ce1d4285745ca695d14ae70d8c145a96a0356ab957460c03b145075b6431

Tx prefix hash: 264b8999b7f2bb7199d7d6762d4053dd5f257b743ef50dd5aac7835de6c08298
Tx public key: d5271c7e4147c6069659a49407f0d5ee2afc599eb3aee54a7f71c269484611c8
Timestamp: 1734177995 Timestamp [UCT]: 2024-12-14 12:06:35 Age [y:d:h:m:s]: 00:094:23:31:31
Block: 1175009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67665 RingCT/type: yes/0
Extra: 01d5271c7e4147c6069659a49407f0d5ee2afc599eb3aee54a7f71c269484611c8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ca6c42483482bd76b71c94fd429d7269d0f13c7d0d81b91c68e09175b958e35 0.600000000000 1661232 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": 1175019, "vin": [ { "gen": { "height": 1175009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ca6c42483482bd76b71c94fd429d7269d0f13c7d0d81b91c68e09175b958e35" } } ], "extra": [ 1, 213, 39, 28, 126, 65, 71, 198, 6, 150, 89, 164, 148, 7, 240, 213, 238, 42, 252, 89, 158, 179, 174, 229, 74, 127, 113, 194, 105, 72, 70, 17, 200, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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