Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da1baffea5773f4744cc2b29d8b9dc5e1a6169d64aebae03afd0e3d43e3f4545

Tx prefix hash: 411a2ad8a6eafdf2f48918aa210ac04d7bfd456c5e16c225546aad47f51f088d
Tx public key: f2dcf4906b21e8801ea619c7c36dc19d97e83a50d2c838367a3a349c6610a9e4
Timestamp: 1735890817 Timestamp [UCT]: 2025-01-03 07:53:37 Age [y:d:h:m:s]: 00:169:11:08:17
Block: 1189189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120749 RingCT/type: yes/0
Extra: 01f2dcf4906b21e8801ea619c7c36dc19d97e83a50d2c838367a3a349c6610a9e4021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08020512774e27ce91afadcf559ac70ae14acacf17c8bdc7cad7a7768f6c47da 0.600000000000 1675694 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": 1189199, "vin": [ { "gen": { "height": 1189189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08020512774e27ce91afadcf559ac70ae14acacf17c8bdc7cad7a7768f6c47da" } } ], "extra": [ 1, 242, 220, 244, 144, 107, 33, 232, 128, 30, 166, 25, 199, 195, 109, 193, 157, 151, 232, 58, 80, 210, 200, 56, 54, 122, 58, 52, 156, 102, 16, 169, 228, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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