Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a6e41f2b39cce5a38c15818a26b5346df69c22198444dab4c53c2d94eb15ad6

Tx prefix hash: 4fcef8cc8191925775b6585cfce0d43df83d62f63c4ca61f2ad0cc3801ab9785
Tx public key: 3b5b3586faaa5215f5f5bde53d54add41c4f2ed9c00e8498f78f5a2bc9e572ad
Timestamp: 1737296004 Timestamp [UCT]: 2025-01-19 14:13:24 Age [y:d:h:m:s]: 00:296:20:34:57
Block: 1200758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209698 RingCT/type: yes/0
Extra: 013b5b3586faaa5215f5f5bde53d54add41c4f2ed9c00e8498f78f5a2bc9e572ad0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb8efe27d8026cc762867f553750b3c4c4669ca8d596411b37ff9cfbc9585e46 0.600000000000 1687403 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": 1200768, "vin": [ { "gen": { "height": 1200758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb8efe27d8026cc762867f553750b3c4c4669ca8d596411b37ff9cfbc9585e46" } } ], "extra": [ 1, 59, 91, 53, 134, 250, 170, 82, 21, 245, 245, 189, 229, 61, 84, 173, 212, 28, 79, 46, 217, 192, 14, 132, 152, 247, 143, 90, 43, 201, 229, 114, 173, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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