Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3949b6853cc91c5e022c384ee53bb72c1aa5fc6a22025d18c5a75137f5dd66e0

Tx prefix hash: cbac8f41e89b9b7624b2c256689d4c57146a280d74999a04da2e115b14e432fa
Tx public key: e1a38adb383a1700653154b1180b3554e3c0ace5055ad98a3fb6f853a565ab7e
Timestamp: 1746134608 Timestamp [UCT]: 2025-05-01 21:23:28 Age [y:d:h:m:s]: 00:200:10:13:29
Block: 1273701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140958 RingCT/type: yes/0
Extra: 01e1a38adb383a1700653154b1180b3554e3c0ace5055ad98a3fb6f853a565ab7e021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbf36989c8a0f5839339151984f2801213ca6b8d1bc086439b93e6d261154b4c 0.600000000000 1760984 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": 1273711, "vin": [ { "gen": { "height": 1273701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbf36989c8a0f5839339151984f2801213ca6b8d1bc086439b93e6d261154b4c" } } ], "extra": [ 1, 225, 163, 138, 219, 56, 58, 23, 0, 101, 49, 84, 177, 24, 11, 53, 84, 227, 192, 172, 229, 5, 90, 217, 138, 63, 182, 248, 83, 165, 101, 171, 126, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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