Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc76562ceb04efaf9f10b9f3f86753e0f9a41ecdf56453fb8024c892f2a295f7

Tx prefix hash: 960064e6e47a16361e00355aca117789c5a69ef8b54bf60af86e2298a3a37e57
Tx public key: e3d27265872bf94282d5380fa925a87ceacb148f273010a0ec0b2c92ab2d6089
Timestamp: 1644603801 Timestamp [UCT]: 2022-02-11 18:23:21 Age [y:d:h:m:s]: 03:263:02:40:11
Block: 436474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 965711 RingCT/type: yes/0
Extra: 01e3d27265872bf94282d5380fa925a87ceacb148f273010a0ec0b2c92ab2d608902110000000d4a0f5013000000000000000000

1 output(s) for total of 21.967505692000 dcy

stealth address amount amount idx
00: a739e285ee6bb4069dc941ec93064fe51e333ea2178a28b03e7bb509c70cfa05 21.967505692000 847857 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": 436484, "vin": [ { "gen": { "height": 436474 } } ], "vout": [ { "amount": 21967505692, "target": { "key": "a739e285ee6bb4069dc941ec93064fe51e333ea2178a28b03e7bb509c70cfa05" } } ], "extra": [ 1, 227, 210, 114, 101, 135, 43, 249, 66, 130, 213, 56, 15, 169, 37, 168, 124, 234, 203, 20, 143, 39, 48, 16, 160, 236, 11, 44, 146, 171, 45, 96, 137, 2, 17, 0, 0, 0, 13, 74, 15, 80, 19, 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