Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39202750e52f7772ee88d452752ac4dff1438c7b00c4fd1baaa812c2479ed161

Tx prefix hash: cdd855bea33125023431c8365ff789af71b408d584c9f7ab06b047240ac18a30
Tx public key: 9150e52a97b9234b800e30a90ed3dd705750d1a6d11f7bbd2dbe1897664a9b49
Timestamp: 1577733266 Timestamp [UCT]: 2019-12-30 19:14:26 Age [y:d:h:m:s]: 05:306:04:40:47
Block: 35264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1366292 RingCT/type: yes/0
Extra: 019150e52a97b9234b800e30a90ed3dd705750d1a6d11f7bbd2dbe1897664a9b4902110000000e8a2ee0d9000000000000000000

1 output(s) for total of 468.998632113000 dcy

stealth address amount amount idx
00: fdffcbd15241a0f7aa602ac5e34ea878ef9cf0d8fc84ea54446d7c5cf0a183f5 468.998632113000 59388 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": 35274, "vin": [ { "gen": { "height": 35264 } } ], "vout": [ { "amount": 468998632113, "target": { "key": "fdffcbd15241a0f7aa602ac5e34ea878ef9cf0d8fc84ea54446d7c5cf0a183f5" } } ], "extra": [ 1, 145, 80, 229, 42, 151, 185, 35, 75, 128, 14, 48, 169, 14, 211, 221, 112, 87, 80, 209, 166, 209, 31, 123, 189, 45, 190, 24, 151, 102, 74, 155, 73, 2, 17, 0, 0, 0, 14, 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