Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e7126b157ac8f302da6065dca8909a62edc8117397a69d53731ef5f8af062e3

Tx prefix hash: 1b4e0753f45d42b80f73a1a7f1124de0b3b118f59f11acb58d42e6d824d762c1
Tx public key: 569a18e97403690529fef5a3b089c393f665fcc7fbe0f4d7c4d853e8604d10c3
Timestamp: 1715796936 Timestamp [UCT]: 2024-05-15 18:15:36 Age [y:d:h:m:s]: 00:328:17:33:56
Block: 1022709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234979 RingCT/type: yes/0
Extra: 01569a18e97403690529fef5a3b089c393f665fcc7fbe0f4d7c4d853e8604d10c30211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7aa7b970900b0f51f7949e0d0828c5d7ea39d95239c9cd27ab19b5497958f45c 0.600000000000 1487390 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": 1022719, "vin": [ { "gen": { "height": 1022709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7aa7b970900b0f51f7949e0d0828c5d7ea39d95239c9cd27ab19b5497958f45c" } } ], "extra": [ 1, 86, 154, 24, 233, 116, 3, 105, 5, 41, 254, 245, 163, 176, 137, 195, 147, 246, 101, 252, 199, 251, 224, 244, 215, 196, 216, 83, 232, 96, 77, 16, 195, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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