Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0674c388cbb3f50b89781c43c87e69b2d0bb5a09934517d67f3098cd6ae7bd1

Tx prefix hash: e6640044c8ada67012e4fb328db86319d3c835e0ce8b1b05ae079733171a25d4
Tx public key: 4e0c5a4132e716b90373526f4d9d01ccccc6c356d13c3c33983889cf09d10065
Timestamp: 1580776141 Timestamp [UCT]: 2020-02-04 00:29:01 Age [y:d:h:m:s]: 05:040:11:40:50
Block: 57957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181162 RingCT/type: yes/0
Extra: 014e0c5a4132e716b90373526f4d9d01ccccc6c356d13c3c33983889cf09d100650211000000284943cd9f000000000000000000

1 output(s) for total of 394.452944773000 dcy

stealth address amount amount idx
00: 03bbe10543bec21625133a116da285e96cd8f12bbf90ad3a3617a09b5d2fecad 394.452944773000 107192 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": 57967, "vin": [ { "gen": { "height": 57957 } } ], "vout": [ { "amount": 394452944773, "target": { "key": "03bbe10543bec21625133a116da285e96cd8f12bbf90ad3a3617a09b5d2fecad" } } ], "extra": [ 1, 78, 12, 90, 65, 50, 231, 22, 185, 3, 115, 82, 111, 77, 157, 1, 204, 204, 198, 195, 86, 209, 60, 60, 51, 152, 56, 137, 207, 9, 209, 0, 101, 2, 17, 0, 0, 0, 40, 73, 67, 205, 159, 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