Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 708a5a631dd01fa73cfbf2e2b755e060c30ea67ccef55142f7de8705d018e391

Tx prefix hash: 658268e9509d81d74386ed47b3accb75874d8cbd217a84c27eff2adf6c2ed6c2
Tx public key: fa7b9c39cd8029f8d08806349460a5baef842d5363a42f1bdd4b1da7b1f8c397
Timestamp: 1739848390 Timestamp [UCT]: 2025-02-18 03:13:10 Age [y:d:h:m:s]: 00:345:05:43:21
Block: 1221630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244447 RingCT/type: yes/0
Extra: 01fa7b9c39cd8029f8d08806349460a5baef842d5363a42f1bdd4b1da7b1f8c397021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a36f17e40349e552898fbcdea1530f7dddaa67f6628e802ae2c86d4e14ca6a6b 0.600000000000 1708475 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": 1221640, "vin": [ { "gen": { "height": 1221630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a36f17e40349e552898fbcdea1530f7dddaa67f6628e802ae2c86d4e14ca6a6b" } } ], "extra": [ 1, 250, 123, 156, 57, 205, 128, 41, 248, 208, 136, 6, 52, 148, 96, 165, 186, 239, 132, 45, 83, 99, 164, 47, 27, 221, 75, 29, 167, 177, 248, 195, 151, 2, 17, 0, 0, 0, 2, 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