Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a4d6dbd2e385e93b57e5563c37e1e7928444d7f4858244ceed2666970dd324e

Tx prefix hash: f566a7d6823a16d1e267c2a6273aef01b6ad0c3277d2f67bc2d54f9eb4b6945a
Tx public key: 32ab2c8b9a2344757540543bbf9cee5b1c4480d25127b80845632073391908c4
Timestamp: 1720098303 Timestamp [UCT]: 2024-07-04 13:05:03 Age [y:d:h:m:s]: 00:273:07:43:07
Block: 1058361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195292 RingCT/type: yes/0
Extra: 0132ab2c8b9a2344757540543bbf9cee5b1c4480d25127b80845632073391908c40211000000028fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf6bed786d92f9b26a7efc1be81c8f3d884ecee2df558882fd93ca0aaebc435b 0.600000000000 1528814 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": 1058371, "vin": [ { "gen": { "height": 1058361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf6bed786d92f9b26a7efc1be81c8f3d884ecee2df558882fd93ca0aaebc435b" } } ], "extra": [ 1, 50, 171, 44, 139, 154, 35, 68, 117, 117, 64, 84, 59, 191, 156, 238, 91, 28, 68, 128, 210, 81, 39, 184, 8, 69, 99, 32, 115, 57, 25, 8, 196, 2, 17, 0, 0, 0, 2, 143, 218, 155, 45, 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