Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33caaa369157e75f4558214bbbef567ba4dc758c054ea1f19c35d08f5840798f

Tx prefix hash: 72d1fb5a9ec8aa29482978a2f4c65468e5477d1433bc0508eaa22f7981ba33d9
Tx public key: 19ce06a62d1f5e2f40e11bb2cd5133dd83df58bcd3fa50e840258d7286fc174b
Timestamp: 1711479124 Timestamp [UCT]: 2024-03-26 18:52:04 Age [y:d:h:m:s]: 01:006:11:04:23
Block: 986937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265551 RingCT/type: yes/0
Extra: 0119ce06a62d1f5e2f40e11bb2cd5133dd83df58bcd3fa50e840258d7286fc174b02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb37ce664599c7757a0c98041a6df32b380b502bfc9e7af1095b0e9c833544ad 0.600000000000 1447174 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": 986947, "vin": [ { "gen": { "height": 986937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb37ce664599c7757a0c98041a6df32b380b502bfc9e7af1095b0e9c833544ad" } } ], "extra": [ 1, 25, 206, 6, 166, 45, 31, 94, 47, 64, 225, 27, 178, 205, 81, 51, 221, 131, 223, 88, 188, 211, 250, 80, 232, 64, 37, 141, 114, 134, 252, 23, 75, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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