Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb4fa4100f5c6b9a99b3664305ed203c1a5f6364f0217e4e062ea84b9ed189de

Tx prefix hash: 173d573f99ce38bd583901f1829f9fc0adbd569ae1b1c3f77585adc914de6bb5
Tx public key: 45e36247b826cb176977d9ea99f56a9a9624531475fde0e77dcf5bff8a5212f7
Timestamp: 1721310406 Timestamp [UCT]: 2024-07-18 13:46:46 Age [y:d:h:m:s]: 00:301:11:02:28
Block: 1068441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215373 RingCT/type: yes/0
Extra: 0145e36247b826cb176977d9ea99f56a9a9624531475fde0e77dcf5bff8a5212f702110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc87eadd091e952bf4fb1f6341440ec43a37cc4cd03719cd2ffe21168d2a0868 0.600000000000 1539518 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": 1068451, "vin": [ { "gen": { "height": 1068441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc87eadd091e952bf4fb1f6341440ec43a37cc4cd03719cd2ffe21168d2a0868" } } ], "extra": [ 1, 69, 227, 98, 71, 184, 38, 203, 23, 105, 119, 217, 234, 153, 245, 106, 154, 150, 36, 83, 20, 117, 253, 224, 231, 125, 207, 91, 255, 138, 82, 18, 247, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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