Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d94db066ba0a4333e651531e19fed3ef6694e8d3f16a12c7672db38785927c6f

Tx prefix hash: d0357c4372524e31cf0d7e775951764f762b224848b341e410825a93018508f3
Tx public key: a5219615fd16071966464efb0d74907fb6cae8d52913ae1b7618c95803fb6d15
Timestamp: 1737029255 Timestamp [UCT]: 2025-01-16 12:07:35 Age [y:d:h:m:s]: 00:339:15:45:00
Block: 1198586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240308 RingCT/type: yes/0
Extra: 01a5219615fd16071966464efb0d74907fb6cae8d52913ae1b7618c95803fb6d15021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 656ea4ef5d2a2b3546e1ae8b51e9589d1182dd0f904c53950817ba0c08fae304 0.600000000000 1685211 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": 1198596, "vin": [ { "gen": { "height": 1198586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "656ea4ef5d2a2b3546e1ae8b51e9589d1182dd0f904c53950817ba0c08fae304" } } ], "extra": [ 1, 165, 33, 150, 21, 253, 22, 7, 25, 102, 70, 78, 251, 13, 116, 144, 127, 182, 202, 232, 213, 41, 19, 174, 27, 118, 24, 201, 88, 3, 251, 109, 21, 2, 17, 0, 0, 0, 5, 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