Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1747932be72082914aaf80c238f2272f96303e402d0a1dab229d4c2f2bf60af

Tx prefix hash: 5bdfecab6b15883ba6323f175fed828edc9ce3467cb29ed37572d546cde78ded
Tx public key: df0b5d8712cb3b9afe09e506e5dc7132b6820e7c1bddccfafc21456fc8caa9be
Timestamp: 1641071777 Timestamp [UCT]: 2022-01-01 21:16:17 Age [y:d:h:m:s]: 02:334:10:14:55
Block: 408418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 757141 RingCT/type: yes/0
Extra: 01df0b5d8712cb3b9afe09e506e5dc7132b6820e7c1bddccfafc21456fc8caa9be021100000010edb0d4a3000000000000000000

1 output(s) for total of 27.211610879000 dcy

stealth address amount amount idx
00: 82474bc317702154f497d361a960ef6d601e1bd7da1eea27798562b66b34b61a 27.211610879000 810453 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": 408428, "vin": [ { "gen": { "height": 408418 } } ], "vout": [ { "amount": 27211610879, "target": { "key": "82474bc317702154f497d361a960ef6d601e1bd7da1eea27798562b66b34b61a" } } ], "extra": [ 1, 223, 11, 93, 135, 18, 203, 59, 154, 254, 9, 229, 6, 229, 220, 113, 50, 182, 130, 14, 124, 27, 221, 204, 250, 252, 33, 69, 111, 200, 202, 169, 190, 2, 17, 0, 0, 0, 16, 237, 176, 212, 163, 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