Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c8c698ebeb09d47fe7484c0d0ffffe0ed717140b3c53f51fa40aa19c8ad5851

Tx prefix hash: 99c8cd784f281ea0627fef01a62a682874411184be79e6d199d602dbbde041d1
Tx public key: 24cb6a25e969a0409825df5bbb4c1a5d3907211518cabc3f7f4099717f160480
Timestamp: 1749396972 Timestamp [UCT]: 2025-06-08 15:36:12 Age [y:d:h:m:s]: 00:161:03:52:11
Block: 1300727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112856 RingCT/type: yes/0
Extra: 0124cb6a25e969a0409825df5bbb4c1a5d3907211518cabc3f7f4099717f16048002110000000bbf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52f622bf4e48007824a94dfad8e48c589f8f0e40fe1dd0ad2f7a0cbd8afef7f2 0.600000000000 1788276 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": 1300737, "vin": [ { "gen": { "height": 1300727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52f622bf4e48007824a94dfad8e48c589f8f0e40fe1dd0ad2f7a0cbd8afef7f2" } } ], "extra": [ 1, 36, 203, 106, 37, 233, 105, 160, 64, 152, 37, 223, 91, 187, 76, 26, 93, 57, 7, 33, 21, 24, 202, 188, 63, 127, 64, 153, 113, 127, 22, 4, 128, 2, 17, 0, 0, 0, 11, 191, 81, 178, 162, 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