Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 124f370434aaa510517edda5df9713a8b6a8e5e8c55ebc178e093fef4192c5b2

Tx prefix hash: 08fe1fcbe7f435a23eb683ef7ff0c5568680ac7d2444b667e09a11b8fe838e5c
Tx public key: cd3dc616b93a5477cdc3395f966266236b6b5b7a8f302ab548a9c340bbcc49f0
Timestamp: 1643331871 Timestamp [UCT]: 2022-01-28 01:04:31 Age [y:d:h:m:s]: 02:307:17:32:50
Block: 426715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 738452 RingCT/type: yes/0
Extra: 01cd3dc616b93a5477cdc3395f966266236b6b5b7a8f302ab548a9c340bbcc49f002110000000c2e6b1fd5000000000000000000

1 output(s) for total of 23.665537898000 dcy

stealth address amount amount idx
00: 77054b94adb78cd045f3ea810e60d9bb4d87ccd8a2e9ae868e523c8e9e0ea532 23.665537898000 835617 of 0

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": 426725, "vin": [ { "gen": { "height": 426715 } } ], "vout": [ { "amount": 23665537898, "target": { "key": "77054b94adb78cd045f3ea810e60d9bb4d87ccd8a2e9ae868e523c8e9e0ea532" } } ], "extra": [ 1, 205, 61, 198, 22, 185, 58, 84, 119, 205, 195, 57, 95, 150, 98, 102, 35, 107, 107, 91, 122, 143, 48, 42, 181, 72, 169, 195, 64, 187, 204, 73, 240, 2, 17, 0, 0, 0, 12, 46, 107, 31, 213, 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