Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ba7bdfaaf77e4b841de87fab2bb07b58635e78a15693dc40a311d647919e96c

Tx prefix hash: e50c57c7c8c39bc9c0a498ba27a285a7b0e5e4f96e70f7ccbd99f210501d9853
Tx public key: 24797654a906198165b1f1b12e306e068528b85384e8d1d4a283a6ad28598082
Timestamp: 1727655088 Timestamp [UCT]: 2024-09-30 00:11:28 Age [y:d:h:m:s]: 00:115:13:09:20
Block: 1121021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82569 RingCT/type: yes/0
Extra: 0124797654a906198165b1f1b12e306e068528b85384e8d1d4a283a6ad2859808202110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec1ab7f0a4edb5e8631cb461e8e832ca14a01f306145ccc4ffc9285b772639d2 0.600000000000 1603144 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": 1121031, "vin": [ { "gen": { "height": 1121021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec1ab7f0a4edb5e8631cb461e8e832ca14a01f306145ccc4ffc9285b772639d2" } } ], "extra": [ 1, 36, 121, 118, 84, 169, 6, 25, 129, 101, 177, 241, 177, 46, 48, 110, 6, 133, 40, 184, 83, 132, 232, 209, 212, 162, 131, 166, 173, 40, 89, 128, 130, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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