Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0561d4b22991e35fd107dcbf75411fc87d63e233ea037d2bfab23b04309fcd53

Tx prefix hash: 4678a8c9381ef5a1ef5b09d1df53ac7db2838b355aa8898d1e45c860ca4639a8
Tx public key: 09c1d4d0471e2c47d647bc5f1657ecdb6fdb955801279fe6aca4d44dbe42f37e
Timestamp: 1704877128 Timestamp [UCT]: 2024-01-10 08:58:48 Age [y:d:h:m:s]: 01:107:10:37:49
Block: 932165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337916 RingCT/type: yes/0
Extra: 0109c1d4d0471e2c47d647bc5f1657ecdb6fdb955801279fe6aca4d44dbe42f37e02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6968656785ee4f7ad0d6f9b4a9c82503a4b9a1adfb002af13f098781d82b86ce 0.600000000000 1390089 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": 932175, "vin": [ { "gen": { "height": 932165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6968656785ee4f7ad0d6f9b4a9c82503a4b9a1adfb002af13f098781d82b86ce" } } ], "extra": [ 1, 9, 193, 212, 208, 71, 30, 44, 71, 214, 71, 188, 95, 22, 87, 236, 219, 111, 219, 149, 88, 1, 39, 159, 230, 172, 164, 212, 77, 190, 66, 243, 126, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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