Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7271ee6ca41856e4d875c1d0887bc5d12e1f3c87935c77f0c86a8f1c0b82561

Tx prefix hash: 4006a53a22760744169a7e5a1f1c2d247f2617208d589b34ab1be16a93cfccb9
Tx public key: d095675d19e9b48fc087d02d60c2b91d3129701a4f9a2a88b6699a1a71e41e37
Timestamp: 1657302696 Timestamp [UCT]: 2022-07-08 17:51:36 Age [y:d:h:m:s]: 03:115:20:52:15
Block: 539479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 862515 RingCT/type: yes/0
Extra: 01d095675d19e9b48fc087d02d60c2b91d3129701a4f9a2a88b6699a1a71e41e37021100000001cb8520c2000000000000000000

1 output(s) for total of 10.011110898000 dcy

stealth address amount amount idx
00: 520f6df52d2f0630aef170d49603b2c1666fcf2cbe721347daa5be8e5fe41505 10.011110898000 969586 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": 539489, "vin": [ { "gen": { "height": 539479 } } ], "vout": [ { "amount": 10011110898, "target": { "key": "520f6df52d2f0630aef170d49603b2c1666fcf2cbe721347daa5be8e5fe41505" } } ], "extra": [ 1, 208, 149, 103, 93, 25, 233, 180, 143, 192, 135, 208, 45, 96, 194, 185, 29, 49, 41, 112, 26, 79, 154, 42, 136, 182, 105, 154, 26, 113, 228, 30, 55, 2, 17, 0, 0, 0, 1, 203, 133, 32, 194, 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