Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54109a72e765a28b334ec25d536fb6b7a76082a8d88773877d543dc87c642d6b

Tx prefix hash: 1308c96df217e11472bfb4b5eeb3dab995c9fb33c7c81842491be75549b05c1f
Tx public key: dd240fe356ae4f865d2756c3fbe271aab55c7eb3d60d30d6e40b5e17ab13a3f3
Timestamp: 1684880610 Timestamp [UCT]: 2023-05-23 22:23:30 Age [y:d:h:m:s]: 01:244:01:37:43
Block: 766644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435836 RingCT/type: yes/0
Extra: 01dd240fe356ae4f865d2756c3fbe271aab55c7eb3d60d30d6e40b5e17ab13a3f3021100000003faf35c9c000000000000000000

1 output(s) for total of 1.769254699000 dcy

stealth address amount amount idx
00: 87ef8fc6f9015aa2933ca27f1eaf516261df418658b24e17f474765e030ffea5 1.769254699000 1215699 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": 766654, "vin": [ { "gen": { "height": 766644 } } ], "vout": [ { "amount": 1769254699, "target": { "key": "87ef8fc6f9015aa2933ca27f1eaf516261df418658b24e17f474765e030ffea5" } } ], "extra": [ 1, 221, 36, 15, 227, 86, 174, 79, 134, 93, 39, 86, 195, 251, 226, 113, 170, 181, 92, 126, 179, 214, 13, 48, 214, 228, 11, 94, 23, 171, 19, 163, 243, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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