Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a1078bd51fb6cc3c8ee39bc2b0fa1089881c0e8e977bf311e907a69bcad7d17

Tx prefix hash: 52a4116301541587cc022847b190cfdd2e404761b4cb8b5a6937ac07d3e35cf3
Tx public key: 15ed622fb2a4f42f7f48541f823d8a628a40a53c633706d00f89638a94b080ee
Timestamp: 1721009839 Timestamp [UCT]: 2024-07-15 02:17:19 Age [y:d:h:m:s]: 00:263:14:05:53
Block: 1065940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188301 RingCT/type: yes/0
Extra: 0115ed622fb2a4f42f7f48541f823d8a628a40a53c633706d00f89638a94b080ee02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd8f63e547097fa07d3eb36078110348166d5dcf632c521241ea4c5f5ae4babc 0.600000000000 1536509 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": 1065950, "vin": [ { "gen": { "height": 1065940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd8f63e547097fa07d3eb36078110348166d5dcf632c521241ea4c5f5ae4babc" } } ], "extra": [ 1, 21, 237, 98, 47, 178, 164, 244, 47, 127, 72, 84, 31, 130, 61, 138, 98, 138, 64, 165, 60, 99, 55, 6, 208, 15, 137, 99, 138, 148, 176, 128, 238, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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