Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67418edf3c3c5c22febcbacac8bca4f960a8e7d1073494c24c684f1dce6469f6

Tx prefix hash: 97ef17cdd6db0c56869e1c66619f04c69dc3b6da1ac5df01c8aadb9cdf2d6d7a
Tx public key: 2c931961462927e8966c21f96b84742d854370d7e9ef36aa2a57bc30cd8bc10f
Timestamp: 1702602170 Timestamp [UCT]: 2023-12-15 01:02:50 Age [y:d:h:m:s]: 02:024:03:43:18
Block: 913313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 537060 RingCT/type: yes/0
Extra: 012c931961462927e8966c21f96b84742d854370d7e9ef36aa2a57bc30cd8bc10f021100000008faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d254025a69fc61a21fd4fc7f28f022379ab136565b1dbe3ecfa5c809d8525d0 0.600000000000 1370579 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": 913323, "vin": [ { "gen": { "height": 913313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d254025a69fc61a21fd4fc7f28f022379ab136565b1dbe3ecfa5c809d8525d0" } } ], "extra": [ 1, 44, 147, 25, 97, 70, 41, 39, 232, 150, 108, 33, 249, 107, 132, 116, 45, 133, 67, 112, 215, 233, 239, 54, 170, 42, 87, 188, 48, 205, 139, 193, 15, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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