Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7aae4d352bc2278269c8e1eeab102f1b08095e782d8ee08aa43f2f4a67ec207

Tx prefix hash: 0004b9d8771492706df142480e257ca0f78d1cedd9fea43a46aa9d93dd563279
Tx public key: 5c2787b5ca6cd5364153afa99dc321ba7eb33eadd4adec971a152edb7db16acd
Timestamp: 1721701912 Timestamp [UCT]: 2024-07-23 02:31:52 Age [y:d:h:m:s]: 01:108:08:23:57
Block: 1071652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335944 RingCT/type: yes/0
Extra: 015c2787b5ca6cd5364153afa99dc321ba7eb33eadd4adec971a152edb7db16acd0211000000018f454fe7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd8331de3fa5152fbfc2e34fae31dc8f2e6bc3dca6584f23649c401e6d02af00 0.600000000000 1543959 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": 1071662, "vin": [ { "gen": { "height": 1071652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd8331de3fa5152fbfc2e34fae31dc8f2e6bc3dca6584f23649c401e6d02af00" } } ], "extra": [ 1, 92, 39, 135, 181, 202, 108, 213, 54, 65, 83, 175, 169, 157, 195, 33, 186, 126, 179, 62, 173, 212, 173, 236, 151, 26, 21, 46, 219, 125, 177, 106, 205, 2, 17, 0, 0, 0, 1, 143, 69, 79, 231, 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