Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 332c311e1e5330794f6df4db704ffbc82aa5de866550464f6e5ede37a0c5eb91

Tx prefix hash: 6e858b3dd970172d84244b14711044effc3402a6526f021b8e3edf8fa306456e
Tx public key: 343dc131d2e4dccf3cae59068f669532b2e15e48f0af04e8b347a65036aae24d
Timestamp: 1705520299 Timestamp [UCT]: 2024-01-17 19:38:19 Age [y:d:h:m:s]: 01:039:04:22:06
Block: 937489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289066 RingCT/type: yes/0
Extra: 01343dc131d2e4dccf3cae59068f669532b2e15e48f0af04e8b347a65036aae24d02110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e6200dba0ac56627f53760c7f90dfdccad20952a11b7e72de4b03f709dd4143 0.600000000000 1395543 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": 937499, "vin": [ { "gen": { "height": 937489 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e6200dba0ac56627f53760c7f90dfdccad20952a11b7e72de4b03f709dd4143" } } ], "extra": [ 1, 52, 61, 193, 49, 210, 228, 220, 207, 60, 174, 89, 6, 143, 102, 149, 50, 178, 225, 94, 72, 240, 175, 4, 232, 179, 71, 166, 80, 54, 170, 226, 77, 2, 17, 0, 0, 0, 12, 122, 156, 244, 199, 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