Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba5f40fb9d692b05ac07b15108447e00781724f3833dd10fb0ce72f01e18c410

Tx prefix hash: 691915d6b20f66a8d468bd1e0865260470ecdf4861f6c6b602b2d617a54f9601
Tx public key: 5c08d405559b1e15f2a5490190b89ad58e54b363afffcee76a4bb6e7a79e181e
Timestamp: 1722029263 Timestamp [UCT]: 2024-07-26 21:27:43 Age [y:d:h:m:s]: 00:255:07:17:40
Block: 1074370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182368 RingCT/type: yes/0
Extra: 015c08d405559b1e15f2a5490190b89ad58e54b363afffcee76a4bb6e7a79e181e02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c8e013e65828739f6152ced18e18042621963dbc943d6f73dc8b68eecfa3379 0.600000000000 1546883 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": 1074380, "vin": [ { "gen": { "height": 1074370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c8e013e65828739f6152ced18e18042621963dbc943d6f73dc8b68eecfa3379" } } ], "extra": [ 1, 92, 8, 212, 5, 85, 155, 30, 21, 242, 165, 73, 1, 144, 184, 154, 213, 142, 84, 179, 99, 175, 255, 206, 231, 106, 75, 182, 231, 167, 158, 24, 30, 2, 17, 0, 0, 0, 1, 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