Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65f55886683f809a4a2275aaf1aaa5e9dca35851f61218e38b22fc3440d11ae5

Tx prefix hash: 75eaf518c7255d659de34e6935271d8eec887846d92a3b0c132fe9157b6f86a2
Tx public key: d48d825ef7acc6d73c5f76bf814e63d5eb610099dbb0f0443b5f2b555f5b4f3e
Timestamp: 1583452572 Timestamp [UCT]: 2020-03-05 23:56:12 Age [y:d:h:m:s]: 04:255:13:00:38
Block: 77067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1077187 RingCT/type: yes/0
Extra: 01d48d825ef7acc6d73c5f76bf814e63d5eb610099dbb0f0443b5f2b555f5b4f3e0211000000068a2ee0d9000000000000000000

1 output(s) for total of 340.914780938000 dcy

stealth address amount amount idx
00: bf743b22f0db57ad7856ccc73844af116f4da1db9e0bb04bf381785dbb0aa1ad 340.914780938000 141897 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": 77077, "vin": [ { "gen": { "height": 77067 } } ], "vout": [ { "amount": 340914780938, "target": { "key": "bf743b22f0db57ad7856ccc73844af116f4da1db9e0bb04bf381785dbb0aa1ad" } } ], "extra": [ 1, 212, 141, 130, 94, 247, 172, 198, 215, 60, 95, 118, 191, 129, 78, 99, 213, 235, 97, 0, 153, 219, 176, 240, 68, 59, 95, 43, 85, 95, 91, 79, 62, 2, 17, 0, 0, 0, 6, 138, 46, 224, 217, 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