Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39d011634e872bae7a067e051b4d158935f36911441bbe07720f6a1a719216d2

Tx prefix hash: 147281a5edff349a6f9c555425785a80bf5bf0620523857d7b771adef24ee9b0
Tx public key: 8d906cfd00c78ec92ba876b47ea03a906b7adf83a91fb37585c5382f6a9f4f8c
Timestamp: 1710673367 Timestamp [UCT]: 2024-03-17 11:02:47 Age [y:d:h:m:s]: 01:235:21:29:01
Block: 980252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427281 RingCT/type: yes/0
Extra: 018d906cfd00c78ec92ba876b47ea03a906b7adf83a91fb37585c5382f6a9f4f8c02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39fd2e6454607baa2a4134ae36850895fbec08717859f6cc6429deadedac363c 0.600000000000 1440317 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": 980262, "vin": [ { "gen": { "height": 980252 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39fd2e6454607baa2a4134ae36850895fbec08717859f6cc6429deadedac363c" } } ], "extra": [ 1, 141, 144, 108, 253, 0, 199, 142, 201, 43, 168, 118, 180, 126, 160, 58, 144, 107, 122, 223, 131, 169, 31, 179, 117, 133, 197, 56, 47, 106, 159, 79, 140, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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