Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25bacbfa3ab76274ee32dff3211f30c1d965eb6abf679c63dd9f2898b6dd819b

Tx prefix hash: bf9425e8f0821a379e488b5611f901cf7eb3705c14918bdee25dedda2167aa31
Tx public key: 035f18df3af64aff24a59e2b3689f9758699b0acee2959f0a5bf618b348ce9b0
Timestamp: 1700664394 Timestamp [UCT]: 2023-11-22 14:46:34 Age [y:d:h:m:s]: 01:059:21:26:51
Block: 897249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304162 RingCT/type: yes/0
Extra: 01035f18df3af64aff24a59e2b3689f9758699b0acee2959f0a5bf618b348ce9b002110000000133af99f4000000000000000000

1 output(s) for total of 0.653193094000 dcy

stealth address amount amount idx
00: b47340f0130c8d2d3b1d1d397570ac8fb0fc3f64d8f801d6d263c23da4a40570 0.653193094000 1353618 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": 897259, "vin": [ { "gen": { "height": 897249 } } ], "vout": [ { "amount": 653193094, "target": { "key": "b47340f0130c8d2d3b1d1d397570ac8fb0fc3f64d8f801d6d263c23da4a40570" } } ], "extra": [ 1, 3, 95, 24, 223, 58, 246, 74, 255, 36, 165, 158, 43, 54, 137, 249, 117, 134, 153, 176, 172, 238, 41, 89, 240, 165, 191, 97, 139, 52, 140, 233, 176, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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