Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ead6538914e2cbbd566d5bbcba216d1f699ff65da46e1f7574d6f7d52dda492e

Tx prefix hash: edc4ce3358604bea8eaa5f12300d60a6be5cf825e60672035bb3c215508ffc42
Tx public key: c90092d04065f3e86b8ebb09394fcf145c0140026df8e8154ab0ffcee0f12db8
Timestamp: 1648521465 Timestamp [UCT]: 2022-03-29 02:37:45 Age [y:d:h:m:s]: 03:217:09:45:22
Block: 468624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 933302 RingCT/type: yes/0
Extra: 01c90092d04065f3e86b8ebb09394fcf145c0140026df8e8154ab0ffcee0f12db8021100000001a272b9cb000000000000000000

1 output(s) for total of 17.189150117000 dcy

stealth address amount amount idx
00: b5991f31fc2e6c129b696aa2a5ac65afd04f212722c4d1aa38c101182278caf2 17.189150117000 887378 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": 468634, "vin": [ { "gen": { "height": 468624 } } ], "vout": [ { "amount": 17189150117, "target": { "key": "b5991f31fc2e6c129b696aa2a5ac65afd04f212722c4d1aa38c101182278caf2" } } ], "extra": [ 1, 201, 0, 146, 208, 64, 101, 243, 232, 107, 142, 187, 9, 57, 79, 207, 20, 92, 1, 64, 2, 109, 248, 232, 21, 74, 176, 255, 206, 224, 241, 45, 184, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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