Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f040b38c14855ce8e7c1d3d032c344e15155c95d6b98179dfa5e203f5fba2643

Tx prefix hash: 308990306664355fd5eef598bd1599bc33c092dd9ab0b2857c31401838d9f05d
Tx public key: cd4f872c6293bfeaed6b6b40a9017617f6920e869d5f41996509e67c7e43c58e
Timestamp: 1736013202 Timestamp [UCT]: 2025-01-04 17:53:22 Age [y:d:h:m:s]: 00:095:12:51:45
Block: 1190188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68061 RingCT/type: yes/0
Extra: 01cd4f872c6293bfeaed6b6b40a9017617f6920e869d5f41996509e67c7e43c58e02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a00392c9b628ffc90c604763bdc7d532eeb366dc5035f52b57da614ff9e48e77 0.600000000000 1676703 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": 1190198, "vin": [ { "gen": { "height": 1190188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a00392c9b628ffc90c604763bdc7d532eeb366dc5035f52b57da614ff9e48e77" } } ], "extra": [ 1, 205, 79, 135, 44, 98, 147, 191, 234, 237, 107, 107, 64, 169, 1, 118, 23, 246, 146, 14, 134, 157, 95, 65, 153, 101, 9, 230, 124, 126, 67, 197, 142, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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