Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5871f350446d77d94e67c7e66501b29a05764c6b40cb84eb4a43af1972f9efe

Tx prefix hash: 8e7ddd706259e481e6e196102cbf2ced74e58543d7c1f96518dd422e678d4a47
Tx public key: 75a3ad99ba258ec8d86d902060e673e9f21d12b05e3d91dc4930fb1d3b0fafd7
Timestamp: 1697249480 Timestamp [UCT]: 2023-10-14 02:11:20 Age [y:d:h:m:s]: 01:194:11:05:20
Block: 869144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400024 RingCT/type: yes/0
Extra: 0175a3ad99ba258ec8d86d902060e673e9f21d12b05e3d91dc4930fb1d3b0fafd702110000000433af99f4000000000000000000

1 output(s) for total of 0.809403649000 dcy

stealth address amount amount idx
00: 1b7fed8ffab96871e1fcf62323f70b47632a0f81f22c6c5d7515724b8e8c1d2e 0.809403649000 1323979 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": 869154, "vin": [ { "gen": { "height": 869144 } } ], "vout": [ { "amount": 809403649, "target": { "key": "1b7fed8ffab96871e1fcf62323f70b47632a0f81f22c6c5d7515724b8e8c1d2e" } } ], "extra": [ 1, 117, 163, 173, 153, 186, 37, 142, 200, 216, 109, 144, 32, 96, 230, 115, 233, 242, 29, 18, 176, 94, 61, 145, 220, 73, 48, 251, 29, 59, 15, 175, 215, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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