Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b3473d279c9b3fb81d013dbe959f36108e0bb6417bcd14ad5fa946e6089e714

Tx prefix hash: d6fc4ae63ce6e19b5cbb97522a25c30e5b134be708825d4892952f1834f16a43
Tx public key: c9eba1ce42c6431ff2407dea5f8757dd03baa1c85453f66012ee9bade9ec96a9
Timestamp: 1687463713 Timestamp [UCT]: 2023-06-22 19:55:13 Age [y:d:h:m:s]: 01:361:01:54:52
Block: 788060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519151 RingCT/type: yes/0
Extra: 01c9eba1ce42c6431ff2407dea5f8757dd03baa1c85453f66012ee9bade9ec96a902110000000175e3f0e9000000000000000000

1 output(s) for total of 1.502554481000 dcy

stealth address amount amount idx
00: 0d9366900781c48e271246cfbc310e7d418d18154c54a250ff6ae11e9cf9a1e5 1.502554481000 1238153 of 0

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": 788070, "vin": [ { "gen": { "height": 788060 } } ], "vout": [ { "amount": 1502554481, "target": { "key": "0d9366900781c48e271246cfbc310e7d418d18154c54a250ff6ae11e9cf9a1e5" } } ], "extra": [ 1, 201, 235, 161, 206, 66, 198, 67, 31, 242, 64, 125, 234, 95, 135, 87, 221, 3, 186, 161, 200, 84, 83, 246, 96, 18, 238, 155, 173, 233, 236, 150, 169, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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