Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c0076cedac110e236e05d7ab3dfe42e03c318e9c5361275f6a4f26cd746ff3b

Tx prefix hash: 72dc5c7fc94fe54bc3f95f7acd43ff601eecce1b6de122eab53e862e00bbb423
Tx public key: 77b647afe15cb26ec914a4add7326036a1d98f2cd179bc92ee6993d55ab29eb0
Timestamp: 1737333619 Timestamp [UCT]: 2025-01-20 00:40:19 Age [y:d:h:m:s]: 00:150:04:54:44
Block: 1201065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107075 RingCT/type: yes/0
Extra: 0177b647afe15cb26ec914a4add7326036a1d98f2cd179bc92ee6993d55ab29eb0021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bdcd57d0a17eadf3f5254e564f04a8fd28d93e28a5a7bde2d41d744b382d47c 0.600000000000 1687714 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": 1201075, "vin": [ { "gen": { "height": 1201065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bdcd57d0a17eadf3f5254e564f04a8fd28d93e28a5a7bde2d41d744b382d47c" } } ], "extra": [ 1, 119, 182, 71, 175, 225, 92, 178, 110, 201, 20, 164, 173, 215, 50, 96, 54, 161, 217, 143, 44, 209, 121, 188, 146, 238, 105, 147, 213, 90, 178, 158, 176, 2, 17, 0, 0, 0, 9, 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