Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98be2a0649c65c5488dec62b0bb5874b3978db1c647aad9b822109e4bca36844

Tx prefix hash: 91aec947d7c3f4ef9597ae56ae05cee012fc0b08102e119852b2f2ad35298a45
Tx public key: fc8bb47ba1f79c3fbbc2e66941c303d8921dc8d6b57d9ccd39ae17750a8705c8
Timestamp: 1737824054 Timestamp [UCT]: 2025-01-25 16:54:14 Age [y:d:h:m:s]: 01:006:19:07:10
Block: 1205136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263173 RingCT/type: yes/0
Extra: 01fc8bb47ba1f79c3fbbc2e66941c303d8921dc8d6b57d9ccd39ae17750a8705c8021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5567fdfe597ab69a6551de4f88107e41d622fde89e84b7139a722be75bbb2095 0.600000000000 1691833 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": 1205146, "vin": [ { "gen": { "height": 1205136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5567fdfe597ab69a6551de4f88107e41d622fde89e84b7139a722be75bbb2095" } } ], "extra": [ 1, 252, 139, 180, 123, 161, 247, 156, 63, 187, 194, 230, 105, 65, 195, 3, 216, 146, 29, 200, 214, 181, 125, 156, 205, 57, 174, 23, 117, 10, 135, 5, 200, 2, 17, 0, 0, 0, 9, 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