Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd1d019342c00e94917843c97aefbb7c4fbeae98b29e630b84ce1613aa960823

Tx prefix hash: c20fed3e6f53a1a1fb07b26f9e5de4aa20e44726ddbd7156e58a9fddffd18c33
Tx public key: 66fa127c2771bdcdc2f8122942b89a5a75f1308e3f2d1c033aa0b990b0be2cb7
Timestamp: 1730908579 Timestamp [UCT]: 2024-11-06 15:56:19 Age [y:d:h:m:s]: 00:216:06:39:42
Block: 1147907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154450 RingCT/type: yes/0
Extra: 0166fa127c2771bdcdc2f8122942b89a5a75f1308e3f2d1c033aa0b990b0be2cb702110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f8c13e245ab1b42632e94b74e1b9dc8215fa32bfe4e23aff4e41a342ab49b5e 0.600000000000 1632620 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": 1147917, "vin": [ { "gen": { "height": 1147907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f8c13e245ab1b42632e94b74e1b9dc8215fa32bfe4e23aff4e41a342ab49b5e" } } ], "extra": [ 1, 102, 250, 18, 124, 39, 113, 189, 205, 194, 248, 18, 41, 66, 184, 154, 90, 117, 241, 48, 142, 63, 45, 28, 3, 58, 160, 185, 144, 176, 190, 44, 183, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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