Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5dccaca72cf42a0b04bc76ebfedf425fa503de38b1e6f3be38f825e317b5b347

Tx prefix hash: 744d5e8ad815f31f0279aed228eb187d5f207a45bde2c692d682fbaa69616823
Tx public key: 69e89ae9f2d47f092cf7447fd463e9a43ba1496400f6af6445396938eb1689e0
Timestamp: 1689240971 Timestamp [UCT]: 2023-07-13 09:36:11 Age [y:d:h:m:s]: 01:272:01:13:23
Block: 802809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455559 RingCT/type: yes/0
Extra: 0169e89ae9f2d47f092cf7447fd463e9a43ba1496400f6af6445396938eb1689e002110000000ee6d27f9c000000000000000000

1 output(s) for total of 1.342643294000 dcy

stealth address amount amount idx
00: f1e1d1d7c6af2a91d850745aa713d308c5741a115ec76531c130a1354cb6c82c 1.342643294000 1253940 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": 802819, "vin": [ { "gen": { "height": 802809 } } ], "vout": [ { "amount": 1342643294, "target": { "key": "f1e1d1d7c6af2a91d850745aa713d308c5741a115ec76531c130a1354cb6c82c" } } ], "extra": [ 1, 105, 232, 154, 233, 242, 212, 127, 9, 44, 247, 68, 127, 212, 99, 233, 164, 59, 161, 73, 100, 0, 246, 175, 100, 69, 57, 105, 56, 235, 22, 137, 224, 2, 17, 0, 0, 0, 14, 230, 210, 127, 156, 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