Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47cc290409950d3c70a03c2845e38c94a5265e236e662d0caa6b2074d5ccccb2

Tx prefix hash: 0bdb865601a1cf6148e6d0d411d4c64bb35f500ad9f7a592c2f3a10773c53708
Tx public key: 3cd8d066e993d37345ee620f623d59ec7780143c55eed5dee3d335e9e1cb79b0
Timestamp: 1729908335 Timestamp [UCT]: 2024-10-26 02:05:35 Age [y:d:h:m:s]: 00:160:19:12:11
Block: 1139669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114713 RingCT/type: yes/0
Extra: 013cd8d066e993d37345ee620f623d59ec7780143c55eed5dee3d335e9e1cb79b0021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7b5658f6b11d15f05ff28693f58ee50ec22e66464a60f895db7dde99722b234 0.600000000000 1623456 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": 1139679, "vin": [ { "gen": { "height": 1139669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7b5658f6b11d15f05ff28693f58ee50ec22e66464a60f895db7dde99722b234" } } ], "extra": [ 1, 60, 216, 208, 102, 233, 147, 211, 115, 69, 238, 98, 15, 98, 61, 89, 236, 119, 128, 20, 60, 85, 238, 213, 222, 227, 211, 53, 233, 225, 203, 121, 176, 2, 17, 0, 0, 0, 2, 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