Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa8fd1346b40b6db6dee4f599b9d0c2dcc0a50ac2b4a032097b08e75ab65cf13

Tx prefix hash: 43c2add26fbb12c38ba167ec56e1f7d5cdea9ec79707d29f7e2b3dd2d3ffb17d
Tx public key: 28660880da9cef02ccc8deaf3f538c732ece7af1a16be24e4b32750b6daf020f
Timestamp: 1704418021 Timestamp [UCT]: 2024-01-05 01:27:01 Age [y:d:h:m:s]: 01:103:08:13:31
Block: 928344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334987 RingCT/type: yes/0
Extra: 0128660880da9cef02ccc8deaf3f538c732ece7af1a16be24e4b32750b6daf020f02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00a5ada7ef237da87f06f9323878b682b7ece6ce49eb5c121072b0b35e5006ce 0.600000000000 1386202 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": 928354, "vin": [ { "gen": { "height": 928344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00a5ada7ef237da87f06f9323878b682b7ece6ce49eb5c121072b0b35e5006ce" } } ], "extra": [ 1, 40, 102, 8, 128, 218, 156, 239, 2, 204, 200, 222, 175, 63, 83, 140, 115, 46, 206, 122, 241, 161, 107, 226, 78, 75, 50, 117, 11, 109, 175, 2, 15, 2, 17, 0, 0, 0, 6, 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