Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8988353922995ebbf08fe149754b04d07653bcb95390319785a42a4ce1977778

Tx prefix hash: 187734e6b3302bb5ad6e8c25ba38d8e28330aeed4a5932e9aa5f183c8a99b0b6
Tx public key: c0e9a8e3433b542d7229f0f0786df91b1ccd252b63135bde14c0300c548520fd
Timestamp: 1748203000 Timestamp [UCT]: 2025-05-25 19:56:40 Age [y:d:h:m:s]: 00:193:07:06:06
Block: 1290838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135872 RingCT/type: yes/0
Extra: 01c0e9a8e3433b542d7229f0f0786df91b1ccd252b63135bde14c0300c548520fd021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f57fa6c4d78dc1006e1e22a14b9913481d312585dcb7a0fca0c2b1eaeee1625 0.600000000000 1778309 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": 1290848, "vin": [ { "gen": { "height": 1290838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f57fa6c4d78dc1006e1e22a14b9913481d312585dcb7a0fca0c2b1eaeee1625" } } ], "extra": [ 1, 192, 233, 168, 227, 67, 59, 84, 45, 114, 41, 240, 240, 120, 109, 249, 27, 28, 205, 37, 43, 99, 19, 91, 222, 20, 192, 48, 12, 84, 133, 32, 253, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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