Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7b2d7206341de56b25475bb42ba405c1bd3c7eb399d56a4a72b474cfc158c09

Tx prefix hash: 22ca6d5b86f314796b450b520db0f2c76af842f3d49d25da4bd95463e6b38825
Tx public key: 958ae6f8e267e6a4949f3b83a5f045a8ef0d18204794bc9b1167b6396992745d
Timestamp: 1702498714 Timestamp [UCT]: 2023-12-13 20:18:34 Age [y:d:h:m:s]: 01:037:20:47:56
Block: 912459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288388 RingCT/type: yes/0
Extra: 01958ae6f8e267e6a4949f3b83a5f045a8ef0d18204794bc9b1167b6396992745d02110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bc8abb0dade613bd19050e4000b2b8e14e0b4a3451968ef00cb8ff5e01b8ab0 0.600000000000 1369687 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": 912469, "vin": [ { "gen": { "height": 912459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bc8abb0dade613bd19050e4000b2b8e14e0b4a3451968ef00cb8ff5e01b8ab0" } } ], "extra": [ 1, 149, 138, 230, 248, 226, 103, 230, 164, 148, 159, 59, 131, 165, 240, 69, 168, 239, 13, 24, 32, 71, 148, 188, 155, 17, 103, 182, 57, 105, 146, 116, 93, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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