Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0568138bced5f3c019f3d6f8410cb099a416b5b915c070f080df0c37c1226b6

Tx prefix hash: 1786c324329359a4658350a40de0c061c6ba6c1ab05b4b2593b836f27718d831
Tx public key: 42448a9594e145de156f7462bd172db473db2b20bfbad1734dceb9f41ae4a4e4
Timestamp: 1738884107 Timestamp [UCT]: 2025-02-06 23:21:47 Age [y:d:h:m:s]: 00:287:02:23:26
Block: 1213689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202932 RingCT/type: yes/0
Extra: 0142448a9594e145de156f7462bd172db473db2b20bfbad1734dceb9f41ae4a4e4021100000012007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6bee0f138f1256b5e00a0a01a8b1a9ddab0418af47c5cc90a6d1821465fff85 0.600000000000 1700470 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": 1213699, "vin": [ { "gen": { "height": 1213689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6bee0f138f1256b5e00a0a01a8b1a9ddab0418af47c5cc90a6d1821465fff85" } } ], "extra": [ 1, 66, 68, 138, 149, 148, 225, 69, 222, 21, 111, 116, 98, 189, 23, 45, 180, 115, 219, 43, 32, 191, 186, 209, 115, 77, 206, 185, 244, 26, 228, 164, 228, 2, 17, 0, 0, 0, 18, 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