Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e06332c0f2394d4b787ab7c12f32005fa73c92d2d18d41080d9dff02d823bcd7

Tx prefix hash: 44657193c6d5b53da0420de89eebbc884baaeb601e50f2950d90b41a9a2fdd8e
Tx public key: 41255698127cb86fa8095d0a4e1c8fb18ec7074a2843299e2a15ec3997ce39f3
Timestamp: 1711695241 Timestamp [UCT]: 2024-03-29 06:54:01 Age [y:d:h:m:s]: 01:026:10:59:09
Block: 988719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279875 RingCT/type: yes/0
Extra: 0141255698127cb86fa8095d0a4e1c8fb18ec7074a2843299e2a15ec3997ce39f302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed2a0dc8dbbc2e008af0219286a910756d54e4c1c5d87b93ad2464a75cc8f4a1 0.600000000000 1449000 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": 988729, "vin": [ { "gen": { "height": 988719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed2a0dc8dbbc2e008af0219286a910756d54e4c1c5d87b93ad2464a75cc8f4a1" } } ], "extra": [ 1, 65, 37, 86, 152, 18, 124, 184, 111, 168, 9, 93, 10, 78, 28, 143, 177, 142, 199, 7, 74, 40, 67, 41, 158, 42, 21, 236, 57, 151, 206, 57, 243, 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