Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09056cf60f3f5081f77c3375b7a9999cdf8eae5a26cb5bc9e654f4497129d828

Tx prefix hash: 675d35715ef31b490104502c7b503b9e14421aec0ccb12c8608ecf61592562f7
Tx public key: 6bd2661d6586bd8b8b0b134388173673da9755ab5e79e8b083358728c505476e
Timestamp: 1639341547 Timestamp [UCT]: 2021-12-12 20:39:07 Age [y:d:h:m:s]: 03:323:12:43:19
Block: 394143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1007700 RingCT/type: yes/0
Extra: 016bd2661d6586bd8b8b0b134388173673da9755ab5e79e8b083358728c505476e021100000001de12510f000000000000000000

1 output(s) for total of 30.341775067000 dcy

stealth address amount amount idx
00: 909ac0fe4dabfe3e03e3ce7d8c58d14e075db817bae6ed4a95bc8f4cf716735f 30.341775067000 791624 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": 394153, "vin": [ { "gen": { "height": 394143 } } ], "vout": [ { "amount": 30341775067, "target": { "key": "909ac0fe4dabfe3e03e3ce7d8c58d14e075db817bae6ed4a95bc8f4cf716735f" } } ], "extra": [ 1, 107, 210, 102, 29, 101, 134, 189, 139, 139, 11, 19, 67, 136, 23, 54, 115, 218, 151, 85, 171, 94, 121, 232, 176, 131, 53, 135, 40, 197, 5, 71, 110, 2, 17, 0, 0, 0, 1, 222, 18, 81, 15, 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