Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42d15c7e2971883acca13b6b0de12aec1e01e163bc4218fcc215f8bc894d186a

Tx prefix hash: ae995d4d931b94b86f7e0f0842aa6fe7c957726d9e03890cccf19925f9740ca6
Tx public key: b71b6c3bb0130644451fd5e98eea0cbbb41435bba40b7c4c701f57815714b210
Timestamp: 1741888334 Timestamp [UCT]: 2025-03-13 17:52:14 Age [y:d:h:m:s]: 00:063:06:47:38
Block: 1238564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45249 RingCT/type: yes/0
Extra: 01b71b6c3bb0130644451fd5e98eea0cbbb41435bba40b7c4c701f57815714b210021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38cf4a06955fd14d8c81aee8fdcbce56e730ebc36b6924dbe1f6d84ab7075a4d 0.600000000000 1725523 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": 1238574, "vin": [ { "gen": { "height": 1238564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38cf4a06955fd14d8c81aee8fdcbce56e730ebc36b6924dbe1f6d84ab7075a4d" } } ], "extra": [ 1, 183, 27, 108, 59, 176, 19, 6, 68, 69, 31, 213, 233, 142, 234, 12, 187, 180, 20, 53, 187, 164, 11, 124, 76, 112, 31, 87, 129, 87, 20, 178, 16, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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