Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: beaf1ccdbe5081a91102b9465a1bd8848c00d17210d43d2f36fe06cadbe421a4

Tx prefix hash: 43e16ea0687f3e21a2e1815eea70b8ad800840a9c5fc0b3dd116c53ccfc02a93
Tx public key: 29748bd00f5aeb343d980cef92c91cb787e292abd0bfe88ba63fc0427c389a74
Timestamp: 1734202345 Timestamp [UCT]: 2024-12-14 18:52:25 Age [y:d:h:m:s]: 00:152:09:17:57
Block: 1175208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108704 RingCT/type: yes/0
Extra: 0129748bd00f5aeb343d980cef92c91cb787e292abd0bfe88ba63fc0427c389a740211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5b8a44fde1aee77e39a21cd9641aa6bb45e159ff2cefeaa6a1069d15a64a3a9 0.600000000000 1661455 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": 1175218, "vin": [ { "gen": { "height": 1175208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5b8a44fde1aee77e39a21cd9641aa6bb45e159ff2cefeaa6a1069d15a64a3a9" } } ], "extra": [ 1, 41, 116, 139, 208, 15, 90, 235, 52, 61, 152, 12, 239, 146, 201, 28, 183, 135, 226, 146, 171, 208, 191, 232, 139, 166, 63, 192, 66, 124, 56, 154, 116, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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