Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ba0b07d7f61d69e86ac83233ac4b30f6767f5c25cdacdc376f6a434b7e73d1d

Tx prefix hash: 2650078a1f7ff9af4ba34df898d66fc0dd693d61ebbe3ad8e344fe6771d37067
Tx public key: ae94f797f6671563bd7baa7250e1f5e8d941d89aca349bfbee9ba0324cb9c44e
Timestamp: 1737879141 Timestamp [UCT]: 2025-01-26 08:12:21 Age [y:d:h:m:s]: 00:142:07:38:49
Block: 1205585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101461 RingCT/type: yes/0
Extra: 01ae94f797f6671563bd7baa7250e1f5e8d941d89aca349bfbee9ba0324cb9c44e021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e03ff0eaf13e720713a8d1ea651821039f057b1dea305a837fea2cf11426ced6 0.600000000000 1692282 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": 1205595, "vin": [ { "gen": { "height": 1205585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e03ff0eaf13e720713a8d1ea651821039f057b1dea305a837fea2cf11426ced6" } } ], "extra": [ 1, 174, 148, 247, 151, 246, 103, 21, 99, 189, 123, 170, 114, 80, 225, 245, 232, 217, 65, 216, 154, 202, 52, 155, 251, 238, 155, 160, 50, 76, 185, 196, 78, 2, 17, 0, 0, 0, 6, 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