Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a715bc288e30d13e48d7cc24abf04d03a3e0b45b14aae81ea774ea3f9eb0ab45

Tx prefix hash: 5ad2454fe14cb44239186197cf1f29e1c7069ed25c9555b4428dd0c66b7e8ef9
Tx public key: 4821834f5ffba726b0b9add4065122621b64a100d64c054c99d690ce3265c977
Timestamp: 1732449114 Timestamp [UCT]: 2024-11-24 11:51:54 Age [y:d:h:m:s]: 00:121:18:02:22
Block: 1160662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86815 RingCT/type: yes/0
Extra: 014821834f5ffba726b0b9add4065122621b64a100d64c054c99d690ce3265c9770211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 093482d03a1e0b240e3ae291cdcea245da94f4feb440c4c49dc7aa0c0c8cda61 0.600000000000 1646311 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": 1160672, "vin": [ { "gen": { "height": 1160662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "093482d03a1e0b240e3ae291cdcea245da94f4feb440c4c49dc7aa0c0c8cda61" } } ], "extra": [ 1, 72, 33, 131, 79, 95, 251, 167, 38, 176, 185, 173, 212, 6, 81, 34, 98, 27, 100, 161, 0, 214, 76, 5, 76, 153, 214, 144, 206, 50, 101, 201, 119, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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