Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 220cd3d328310f2f9c1deed1f7e4dcfdce2fb425e99d2f46030039b43e9718bd

Tx prefix hash: 3dc279ffca1a4807565eb0ad575afa70ea99d78455e7af942c528d1fe55a5ef7
Tx public key: 2aff5ab4dc6c33a09f740cc1fbfec10cdf1dbb78518a8322f2309e1e943b194c
Timestamp: 1728144764 Timestamp [UCT]: 2024-10-05 16:12:44 Age [y:d:h:m:s]: 00:169:10:53:47
Block: 1125079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120890 RingCT/type: yes/0
Extra: 012aff5ab4dc6c33a09f740cc1fbfec10cdf1dbb78518a8322f2309e1e943b194c021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dc4cd62546c9886402395408248c02170d4abe7faf1df2209524c1d411b7218 0.600000000000 1607752 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": 1125089, "vin": [ { "gen": { "height": 1125079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dc4cd62546c9886402395408248c02170d4abe7faf1df2209524c1d411b7218" } } ], "extra": [ 1, 42, 255, 90, 180, 220, 108, 51, 160, 159, 116, 12, 193, 251, 254, 193, 12, 223, 29, 187, 120, 81, 138, 131, 34, 242, 48, 158, 30, 148, 59, 25, 76, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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