Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1189aaa0a7c3db1dc7602a03f6b62c77268def8b6beda5a44f85d25fa75b564

Tx prefix hash: 1f9073c15ab76356e15e9c3c79bdf6d519e934f33f140eefba742c13981a3ab9
Tx public key: 7241f74c369de82c9caeb4cbf7b49b625b684ca3bff66e1b434ac627663c6569
Timestamp: 1745529419 Timestamp [UCT]: 2025-04-24 21:16:59 Age [y:d:h:m:s]: 00:280:05:01:24
Block: 1268695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197902 RingCT/type: yes/0
Extra: 017241f74c369de82c9caeb4cbf7b49b625b684ca3bff66e1b434ac627663c6569021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a409c75ac22c48c7e4233a8cfa7d50f06801b7d8b0f3fd16c38dffdd03027ff9 0.600000000000 1755926 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": 1268705, "vin": [ { "gen": { "height": 1268695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a409c75ac22c48c7e4233a8cfa7d50f06801b7d8b0f3fd16c38dffdd03027ff9" } } ], "extra": [ 1, 114, 65, 247, 76, 54, 157, 232, 44, 156, 174, 180, 203, 247, 180, 155, 98, 91, 104, 76, 163, 191, 246, 110, 27, 67, 74, 198, 39, 102, 60, 101, 105, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 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