Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e919ed5ccfac9a8347badb0c16950387c6381381037d0f227e61cefaa46a2c1f

Tx prefix hash: 735aa102229dd669517046f63fbee915376232aeecbc967d89cd6045968757fe
Tx public key: aad76b926f37ea5c61b0cbfc4c8e7e9c9ace8c60dbca1e5f7815f351b06ae141
Timestamp: 1672892390 Timestamp [UCT]: 2023-01-05 04:19:50 Age [y:d:h:m:s]: 02:104:00:49:24
Block: 667863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 596056 RingCT/type: yes/0
Extra: 01aad76b926f37ea5c61b0cbfc4c8e7e9c9ace8c60dbca1e5f7815f351b06ae14102110000000252542ceb000000000000000000

1 output(s) for total of 3.759175471000 dcy

stealth address amount amount idx
00: b3591db6f2ab27bbfb0ede25894fef45cb6345796d0fc925ca503b7451a90dd4 3.759175471000 1109082 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": 667873, "vin": [ { "gen": { "height": 667863 } } ], "vout": [ { "amount": 3759175471, "target": { "key": "b3591db6f2ab27bbfb0ede25894fef45cb6345796d0fc925ca503b7451a90dd4" } } ], "extra": [ 1, 170, 215, 107, 146, 111, 55, 234, 92, 97, 176, 203, 252, 76, 142, 126, 156, 154, 206, 140, 96, 219, 202, 30, 95, 120, 21, 243, 81, 176, 106, 225, 65, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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