Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 510b7e092ba12df3e2e953844f252c1c7d7b283cd6363b8c8ddd58a5c525fcc7

Tx prefix hash: c5c71bc65583eaa0d0ec61ce6bfabc28c10e68f499e26b4c101ab2592040fb46
Tx public key: 9e1c72fd60a68ab3faf9a21ea0f73f3870da966bbd7da1240f78064718bfb419
Timestamp: 1577742777 Timestamp [UCT]: 2019-12-30 21:52:57 Age [y:d:h:m:s]: 04:332:04:02:03
Block: 35344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126456 RingCT/type: yes/0
Extra: 019e1c72fd60a68ab3faf9a21ea0f73f3870da966bbd7da1240f78064718bfb41902110000003978873133000000000000000000

1 output(s) for total of 468.696284193000 dcy

stealth address amount amount idx
00: 00f63ddb399ebd9c03ff10fe3c0d1597f7355235c7ac745f38967c31da43f3f3 468.696284193000 59542 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": 35354, "vin": [ { "gen": { "height": 35344 } } ], "vout": [ { "amount": 468696284193, "target": { "key": "00f63ddb399ebd9c03ff10fe3c0d1597f7355235c7ac745f38967c31da43f3f3" } } ], "extra": [ 1, 158, 28, 114, 253, 96, 166, 138, 179, 250, 249, 162, 30, 160, 247, 63, 56, 112, 218, 150, 107, 189, 125, 161, 36, 15, 120, 6, 71, 24, 191, 180, 25, 2, 17, 0, 0, 0, 57, 120, 135, 49, 51, 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