Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fe8d81b813e8c33b66d3fff7a4e607006595a6b93f0593cb743315737dbee1a

Tx prefix hash: 74b08062acd5a48d1522e8476570aead7f3d43f4dcfa6abc447c3d66a5ba49a0
Tx public key: 06b97e1c791610a81d8cd9f988b1d1c1525a999fdc7f457d6f75ea1b18ae4f44
Timestamp: 1736196807 Timestamp [UCT]: 2025-01-06 20:53:27 Age [y:d:h:m:s]: 00:350:05:36:27
Block: 1191699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247874 RingCT/type: yes/0
Extra: 0106b97e1c791610a81d8cd9f988b1d1c1525a999fdc7f457d6f75ea1b18ae4f44021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf12de49ae398efc809daa671839ce5b9888894da2f36042eb472c7aa084cbfe 0.600000000000 1678240 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": 1191709, "vin": [ { "gen": { "height": 1191699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf12de49ae398efc809daa671839ce5b9888894da2f36042eb472c7aa084cbfe" } } ], "extra": [ 1, 6, 185, 126, 28, 121, 22, 16, 168, 29, 140, 217, 249, 136, 177, 209, 193, 82, 90, 153, 159, 220, 127, 69, 125, 111, 117, 234, 27, 24, 174, 79, 68, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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