Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f85e8a16016a66e7fcf727e38a24d60164b31f070f1d11679e896a83e40bc269

Tx prefix hash: 0843209af8337c41883e63fb81961864d5dc83c2eb4eb5ee560302ea909aa6be
Tx public key: 2e115b71d204188d8a984c0e8d0a5828bcbabb94f523d4563059d6716e758374
Timestamp: 1718849170 Timestamp [UCT]: 2024-06-20 02:06:10 Age [y:d:h:m:s]: 00:288:08:50:32
Block: 1048019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206058 RingCT/type: yes/0
Extra: 012e115b71d204188d8a984c0e8d0a5828bcbabb94f523d4563059d6716e75837402110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04416dad9a2aaab33a119d9e8eba4b78cf51e2a673d941e1dd49b9d639c9f468 0.600000000000 1517994 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": 1048029, "vin": [ { "gen": { "height": 1048019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04416dad9a2aaab33a119d9e8eba4b78cf51e2a673d941e1dd49b9d639c9f468" } } ], "extra": [ 1, 46, 17, 91, 113, 210, 4, 24, 141, 138, 152, 76, 14, 141, 10, 88, 40, 188, 186, 187, 148, 245, 35, 212, 86, 48, 89, 214, 113, 110, 117, 131, 116, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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