Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0ce1c3c53d94bce0f899fd5f4bf3be77c29129f0e5169ab7ac4d9520de2721f

Tx prefix hash: 648a04f3a86aac25049ff8d3c190ffbd09dc0a7010a370b47fe0303db1938d01
Tx public key: 1cd6d8a643d3c4704acffe76cfea0a9f2fb5467444637b0d6ff000d0b380e6fd
Timestamp: 1726750377 Timestamp [UCT]: 2024-09-19 12:52:57 Age [y:d:h:m:s]: 01:051:03:21:39
Block: 1113517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294963 RingCT/type: yes/0
Extra: 011cd6d8a643d3c4704acffe76cfea0a9f2fb5467444637b0d6ff000d0b380e6fd021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ec347cc179c9dc4eae1a01d38c17bb32f86f59c329273e60bb0c5de4d4b7a08 0.600000000000 1593216 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": 1113527, "vin": [ { "gen": { "height": 1113517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ec347cc179c9dc4eae1a01d38c17bb32f86f59c329273e60bb0c5de4d4b7a08" } } ], "extra": [ 1, 28, 214, 216, 166, 67, 211, 196, 112, 74, 207, 254, 118, 207, 234, 10, 159, 47, 181, 70, 116, 68, 99, 123, 13, 111, 240, 0, 208, 179, 128, 230, 253, 2, 17, 0, 0, 0, 3, 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