Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f58622cf4ea1205cdc7bfa43a8ffc8bbc1df9c3e5af61faf2f9f3a25c5234dea

Tx prefix hash: 0473f799b4acaecdafddc8963457d10d6105141f0dd3e051a590e86c8a91c984
Tx public key: 5aa3fc63ab3a7753e470deb15b24912d5d8cb1f12fd0e01f67174c1bfafd25e8
Timestamp: 1736315787 Timestamp [UCT]: 2025-01-08 05:56:27 Age [y:d:h:m:s]: 00:082:14:27:55
Block: 1192680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58818 RingCT/type: yes/0
Extra: 015aa3fc63ab3a7753e470deb15b24912d5d8cb1f12fd0e01f67174c1bfafd25e8021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aafe3549d5eb4df48bccbb3817df94babb8f638604d31bfcbbc320e44ee411e5 0.600000000000 1679235 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": 1192690, "vin": [ { "gen": { "height": 1192680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aafe3549d5eb4df48bccbb3817df94babb8f638604d31bfcbbc320e44ee411e5" } } ], "extra": [ 1, 90, 163, 252, 99, 171, 58, 119, 83, 228, 112, 222, 177, 91, 36, 145, 45, 93, 140, 177, 241, 47, 208, 224, 31, 103, 23, 76, 27, 250, 253, 37, 232, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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