Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7cd7dcafae1edb605009ad382e5c3282bacb0ef765a1b254a62ca49a878d21d

Tx prefix hash: b48cc639618369c9dc09d8a8dd0ed173d63d72a76081de140f17f86d0c78e710
Tx public key: 8cdc175d9ffe2d9418474f81c5d73d3eacbf92f15e3dd0ce8f70fa01a1422d35
Timestamp: 1632092032 Timestamp [UCT]: 2021-09-19 22:53:52 Age [y:d:h:m:s]: 03:108:05:01:19
Block: 337157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 853325 RingCT/type: yes/0
Extra: 018cdc175d9ffe2d9418474f81c5d73d3eacbf92f15e3dd0ce8f70fa01a1422d350211000000183fc41461000000000000000000

1 output(s) for total of 46.866156106000 dcy

stealth address amount amount idx
00: 29d54ec878e5f93ef63a52be822903bc166803c0468bc558c3666e221b3d0af6 46.866156106000 694362 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": 337167, "vin": [ { "gen": { "height": 337157 } } ], "vout": [ { "amount": 46866156106, "target": { "key": "29d54ec878e5f93ef63a52be822903bc166803c0468bc558c3666e221b3d0af6" } } ], "extra": [ 1, 140, 220, 23, 93, 159, 254, 45, 148, 24, 71, 79, 129, 197, 215, 61, 62, 172, 191, 146, 241, 94, 61, 208, 206, 143, 112, 250, 1, 161, 66, 45, 53, 2, 17, 0, 0, 0, 24, 63, 196, 20, 97, 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