Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c29736690889c07b40e1ad9260577d33dac23438ebbc50931b32cc3ea72b0ff7

Tx prefix hash: d0c1183d5df82a787e5c1e341bedad08f7868cff44d1f3405dc19eed676ab59a
Tx public key: 7d6f2ba7c1819ef61191fa2df351f742f96e962e6223459387a777f1182a59a9
Timestamp: 1644786837 Timestamp [UCT]: 2022-02-13 21:13:57 Age [y:d:h:m:s]: 03:264:15:43:55
Block: 437980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 966816 RingCT/type: yes/0
Extra: 017d6f2ba7c1819ef61191fa2df351f742f96e962e6223459387a777f1182a59a90211000000024a0f5013000000000000000000

1 output(s) for total of 21.716545501000 dcy

stealth address amount amount idx
00: bb720230e586e9ce27b5abb1dc4a93d7fdf5c5f2db36ab2dbfc061a934792a73 21.716545501000 849747 of 0

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": 437990, "vin": [ { "gen": { "height": 437980 } } ], "vout": [ { "amount": 21716545501, "target": { "key": "bb720230e586e9ce27b5abb1dc4a93d7fdf5c5f2db36ab2dbfc061a934792a73" } } ], "extra": [ 1, 125, 111, 43, 167, 193, 129, 158, 246, 17, 145, 250, 45, 243, 81, 247, 66, 249, 110, 150, 46, 98, 35, 69, 147, 135, 167, 119, 241, 24, 42, 89, 169, 2, 17, 0, 0, 0, 2, 74, 15, 80, 19, 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