Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbb1b6a2a2c9589cbee6cabaadcd52acb68bfce95a49f926334c73674fbfa046

Tx prefix hash: 7598cb8e13acf08beaa2c613fe1a0d519437b192c4b4d567e998b9407a88532b
Tx public key: abb78d70b38cc2cf173f15b4e53c390ad5ba6b3c9a5c4defc591999e2c203fc9
Timestamp: 1715473568 Timestamp [UCT]: 2024-05-12 00:26:08 Age [y:d:h:m:s]: 00:314:03:40:21
Block: 1020058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224520 RingCT/type: yes/0
Extra: 01abb78d70b38cc2cf173f15b4e53c390ad5ba6b3c9a5c4defc591999e2c203fc902110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51fffc636808e2af1fb5ed3ae867294e4e851f0eeace80f876e9a4996c534398 0.600000000000 1484117 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": 1020068, "vin": [ { "gen": { "height": 1020058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51fffc636808e2af1fb5ed3ae867294e4e851f0eeace80f876e9a4996c534398" } } ], "extra": [ 1, 171, 183, 141, 112, 179, 140, 194, 207, 23, 63, 21, 180, 229, 60, 57, 10, 213, 186, 107, 60, 154, 92, 77, 239, 197, 145, 153, 158, 44, 32, 63, 201, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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