Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e30866f30ed11bb90916b5f1114a073910b85bece1d45d16c7c69b3412b48414

Tx prefix hash: a3eaa2c3205ce1000e2dcfd8057e336b23ffd5fb3b87bc8bbe497d6d31c91993
Tx public key: 08be3584b06625a8444b0cb279e14b93a4b0133e873e5dc263da5097c8f641d8
Timestamp: 1580880011 Timestamp [UCT]: 2020-02-05 05:20:11 Age [y:d:h:m:s]: 04:328:05:25:40
Block: 58706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126255 RingCT/type: yes/0
Extra: 0108be3584b06625a8444b0cb279e14b93a4b0133e873e5dc263da5097c8f641d8021100000002b221b3d1000000000000000000

1 output(s) for total of 392.178221059000 dcy

stealth address amount amount idx
00: 37807a596a38d1e61f114037ad0a9a8ef65ec5b0266b041eda22dd6088c20591 392.178221059000 108530 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": 58716, "vin": [ { "gen": { "height": 58706 } } ], "vout": [ { "amount": 392178221059, "target": { "key": "37807a596a38d1e61f114037ad0a9a8ef65ec5b0266b041eda22dd6088c20591" } } ], "extra": [ 1, 8, 190, 53, 132, 176, 102, 37, 168, 68, 75, 12, 178, 121, 225, 75, 147, 164, 176, 19, 62, 135, 62, 93, 194, 99, 218, 80, 151, 200, 246, 65, 216, 2, 17, 0, 0, 0, 2, 178, 33, 179, 209, 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