Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be58b3b688c0ef4450b6d994f30e2bd66e66d8bb658ea51be62a005cc387fdc6

Tx prefix hash: 4391260cd495b1bcc6ed04cd3740a77a47136df1314ef36a26743f7d55ababd4
Tx public key: ba524f6ea1a03125d994ed289e164ace9ea74580fb3083e83d1cd2b0a7d65443
Timestamp: 1760657511 Timestamp [UCT]: 2025-10-16 23:31:51 Age [y:d:h:m:s]: 00:041:10:48:15
Block: 1391519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29670 RingCT/type: yes/0
Extra: 01ba524f6ea1a03125d994ed289e164ace9ea74580fb3083e83d1cd2b0a7d654430211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c9763152292b2dd81d3f6a4cda1ec8eddac2d1b42a730f3b28a2c88fe79ec82 0.600000000000 1879766 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": 1391529, "vin": [ { "gen": { "height": 1391519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c9763152292b2dd81d3f6a4cda1ec8eddac2d1b42a730f3b28a2c88fe79ec82" } } ], "extra": [ 1, 186, 82, 79, 110, 161, 160, 49, 37, 217, 148, 237, 40, 158, 22, 74, 206, 158, 167, 69, 128, 251, 48, 131, 232, 61, 28, 210, 176, 167, 214, 84, 67, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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