Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6a147c3ccbf0260deb38621bc5dae751ec4c7ce97fc8471bc83d4c4f41c4264

Tx prefix hash: ba8f072fc050ddf764654ccc69bb4f10e579f90f47c709f96760ebbfee55e376
Tx public key: caad5d048f0e811b1bef94516ec1d3edb840b8e2d6bc433fac9774a5d15d714c
Timestamp: 1704453657 Timestamp [UCT]: 2024-01-05 11:20:57 Age [y:d:h:m:s]: 01:165:07:06:59
Block: 928649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379174 RingCT/type: yes/0
Extra: 01caad5d048f0e811b1bef94516ec1d3edb840b8e2d6bc433fac9774a5d15d714c02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3526368bb9b68cdcab65649c9ec907678ca30304cf6b6c843d1416bcfd1d4cd5 0.600000000000 1386509 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": 928659, "vin": [ { "gen": { "height": 928649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3526368bb9b68cdcab65649c9ec907678ca30304cf6b6c843d1416bcfd1d4cd5" } } ], "extra": [ 1, 202, 173, 93, 4, 143, 14, 129, 27, 27, 239, 148, 81, 110, 193, 211, 237, 184, 64, 184, 226, 214, 188, 67, 63, 172, 151, 116, 165, 209, 93, 113, 76, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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