Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75c731b35817b33049d0cec9289dc637f1b76bb7f5902ddaa8ea64ac97c4ae7d

Tx prefix hash: c0ce962855cd9893944cc754c43312829acafdda4a8e3361ee9c9c3f2ca830eb
Tx public key: 5f9543839f07e29a0c2fbb1db725afa42a42249ab5b6f3f5cffd1e640c1a1339
Timestamp: 1577711322 Timestamp [UCT]: 2019-12-30 13:08:42 Age [y:d:h:m:s]: 05:034:09:27:07
Block: 35042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1174328 RingCT/type: yes/0
Extra: 015f9543839f07e29a0c2fbb1db725afa42a42249ab5b6f3f5cffd1e640c1a133902110000000a8a2ee0d9000000000000000000

1 output(s) for total of 469.846075777000 dcy

stealth address amount amount idx
00: bbc3c8d3773aa52fc44eca97f03e7a9238f50b8a0a459eacf073b7b1cb1f10d2 469.846075777000 59027 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": 35052, "vin": [ { "gen": { "height": 35042 } } ], "vout": [ { "amount": 469846075777, "target": { "key": "bbc3c8d3773aa52fc44eca97f03e7a9238f50b8a0a459eacf073b7b1cb1f10d2" } } ], "extra": [ 1, 95, 149, 67, 131, 159, 7, 226, 154, 12, 47, 187, 29, 183, 37, 175, 164, 42, 66, 36, 154, 181, 182, 243, 245, 207, 253, 30, 100, 12, 26, 19, 57, 2, 17, 0, 0, 0, 10, 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