Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1541cf84594f783197cb6e98fe6d85358811ac0d78dd6407a221d491f6c6f4ea

Tx prefix hash: 77c5f8c032e9b6b4e16de4b9a51aa6bb98c77e94656883bc257a811457c58a16
Tx public key: 6cbd108e424e1e1157475a793f48ee3e83cf1cc70b55f374abcd59d3d8e47333
Timestamp: 1709732281 Timestamp [UCT]: 2024-03-06 13:38:01 Age [y:d:h:m:s]: 01:100:18:25:08
Block: 972441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332969 RingCT/type: yes/0
Extra: 016cbd108e424e1e1157475a793f48ee3e83cf1cc70b55f374abcd59d3d8e4733302110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4123be2101b9a43cfc406cf89a89b18abed6047ca4154063b4cb2140cf8781d1 0.600000000000 1432354 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": 972451, "vin": [ { "gen": { "height": 972441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4123be2101b9a43cfc406cf89a89b18abed6047ca4154063b4cb2140cf8781d1" } } ], "extra": [ 1, 108, 189, 16, 142, 66, 78, 30, 17, 87, 71, 90, 121, 63, 72, 238, 62, 131, 207, 28, 199, 11, 85, 243, 116, 171, 205, 89, 211, 216, 228, 115, 51, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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