Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb3ea2859e1dbcc00c163b78ebde8d2b05f7d1047b5bb7c0f44844856836371c

Tx prefix hash: 447b84dda836d9ff14cbd63e98b655a33bf6a7f48c2675edd791ce2df8d1ec8a
Tx public key: d2afed7500e49832f6a0e42d694248b45316fddb12772de99dfef11574e4f6bc
Timestamp: 1704948590 Timestamp [UCT]: 2024-01-11 04:49:50 Age [y:d:h:m:s]: 01:087:12:29:26
Block: 932742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323658 RingCT/type: yes/0
Extra: 01d2afed7500e49832f6a0e42d694248b45316fddb12772de99dfef11574e4f6bc02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e466b0f2e4c6e3c2dd7c822066da66f71825d38c040d5695e6bbc8de9f131e25 0.600000000000 1390682 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": 932752, "vin": [ { "gen": { "height": 932742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e466b0f2e4c6e3c2dd7c822066da66f71825d38c040d5695e6bbc8de9f131e25" } } ], "extra": [ 1, 210, 175, 237, 117, 0, 228, 152, 50, 246, 160, 228, 45, 105, 66, 72, 180, 83, 22, 253, 219, 18, 119, 45, 233, 157, 254, 241, 21, 116, 228, 246, 188, 2, 17, 0, 0, 0, 2, 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