Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5fcd0c2e74987bd3a82bb277b9b6e49931f5303c0eed4fe5820d8fe582dbd33

Tx prefix hash: 7c16bfdb4b69fd91b7c262687bbbec8f0f2693e2645993c7100e3043b8102e5c
Tx public key: 17dbdcac0641dfdea8911ca2783b1c73b00d2bbd7d81d27b6e4d3df0d204233e
Timestamp: 1704991124 Timestamp [UCT]: 2024-01-11 16:38:44 Age [y:d:h:m:s]: 01:314:05:21:33
Block: 933118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483400 RingCT/type: yes/0
Extra: 0117dbdcac0641dfdea8911ca2783b1c73b00d2bbd7d81d27b6e4d3df0d204233e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 834cbba2f6fd4b7b909eeb712f3911e9ec786d3164ff7d0e08c0cb783c2b1496 0.600000000000 1391074 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": 933128, "vin": [ { "gen": { "height": 933118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "834cbba2f6fd4b7b909eeb712f3911e9ec786d3164ff7d0e08c0cb783c2b1496" } } ], "extra": [ 1, 23, 219, 220, 172, 6, 65, 223, 222, 168, 145, 28, 162, 120, 59, 28, 115, 176, 13, 43, 189, 125, 129, 210, 123, 110, 77, 61, 240, 210, 4, 35, 62, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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