Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec0cd9ec1559ecc3df2e16962646e21711f976224c28eb9c1abc66e049f03d12

Tx prefix hash: 3ac68450ab3abb715e89dc7904c1d4e154a78ce2f8fb324e4948e0f5093eab84
Tx public key: fcb3789aacde37581d9a47b84274aae5afa760e95b88eb29864f3022eaf1c569
Timestamp: 1705033574 Timestamp [UCT]: 2024-01-12 04:26:14 Age [y:d:h:m:s]: 00:308:04:27:53
Block: 933455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220681 RingCT/type: yes/0
Extra: 01fcb3789aacde37581d9a47b84274aae5afa760e95b88eb29864f3022eaf1c569021100000001ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e85f7ebc8f1b627a2894ba5a5aa27c1b76c797f01a9fc382007be7254853d07 0.600000000000 1391417 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": 933465, "vin": [ { "gen": { "height": 933455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e85f7ebc8f1b627a2894ba5a5aa27c1b76c797f01a9fc382007be7254853d07" } } ], "extra": [ 1, 252, 179, 120, 154, 172, 222, 55, 88, 29, 154, 71, 184, 66, 116, 170, 229, 175, 167, 96, 233, 91, 136, 235, 41, 134, 79, 48, 34, 234, 241, 197, 105, 2, 17, 0, 0, 0, 1, 172, 50, 141, 17, 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