Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe7ec2d38409c7240f76f900b4547ca3e07121e10f5683abe6d313a0f75dd4b6

Tx prefix hash: 0cd6c81305f3c9bd4e8f746928080b97ed97ebb5cc4eab6fd8a5032aa99a5e99
Tx public key: 073c0b6dc004ae0a910b4f35e1e5f583fd486e706b4f1e2d8179d3ccb81ed913
Timestamp: 1720810911 Timestamp [UCT]: 2024-07-12 19:01:51 Age [y:d:h:m:s]: 00:267:08:49:52
Block: 1064286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191008 RingCT/type: yes/0
Extra: 01073c0b6dc004ae0a910b4f35e1e5f583fd486e706b4f1e2d8179d3ccb81ed91302110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fe3968dbb7bfdceeaf1c01834b620e9ba9e518d43e6757e74183904465e0242 0.600000000000 1534809 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": 1064296, "vin": [ { "gen": { "height": 1064286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fe3968dbb7bfdceeaf1c01834b620e9ba9e518d43e6757e74183904465e0242" } } ], "extra": [ 1, 7, 60, 11, 109, 192, 4, 174, 10, 145, 11, 79, 53, 225, 229, 245, 131, 253, 72, 110, 112, 107, 79, 30, 45, 129, 121, 211, 204, 184, 30, 217, 19, 2, 17, 0, 0, 0, 15, 145, 225, 60, 4, 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