Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a58bd8cdb2eb8adb956d2f66de30632bd1ca3a63afb492ca7e9d1a6ab9e805cf

Tx prefix hash: b96942d2c95438d9ffd630709b204bcd9f971bcc8a1562b622c23a1db5644e11
Tx public key: 50c18c662428c7400b1f4e405c8ef2e06acbaf2aaeae79aef162be24f53009dc
Timestamp: 1732353420 Timestamp [UCT]: 2024-11-23 09:17:00 Age [y:d:h:m:s]: 00:000:19:42:25
Block: 1159877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 581 RingCT/type: yes/0
Extra: 0150c18c662428c7400b1f4e405c8ef2e06acbaf2aaeae79aef162be24f53009dc021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6eac5e9d8cb6a0ecf606110ff4f99a44e022c3c0b024608b4078b6f0b3ea1a8d 0.600000000000 1645516 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": 1159887, "vin": [ { "gen": { "height": 1159877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6eac5e9d8cb6a0ecf606110ff4f99a44e022c3c0b024608b4078b6f0b3ea1a8d" } } ], "extra": [ 1, 80, 193, 140, 102, 36, 40, 199, 64, 11, 31, 78, 64, 92, 142, 242, 224, 106, 203, 175, 42, 174, 174, 121, 174, 241, 98, 190, 36, 245, 48, 9, 220, 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