Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 665a3b775e6cdfbe974666b759b3f4533bd63982c96b477e5d88779609141c0d

Tx prefix hash: 8e29274d4e1458d19f04e1842ee7ac670aa561643f540b4496bff9813acd01b6
Tx public key: 77f8b53597742a927117d1656a0a118aab8cc4b7a2e29a87cb3e2e71afbb72c6
Timestamp: 1632362184 Timestamp [UCT]: 2021-09-23 01:56:24 Age [y:d:h:m:s]: 03:165:09:57:19
Block: 339148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 894224 RingCT/type: yes/0
Extra: 0177f8b53597742a927117d1656a0a118aab8cc4b7a2e29a87cb3e2e71afbb72c60211000000025410958b000000000000000000

1 output(s) for total of 46.159630357000 dcy

stealth address amount amount idx
00: bdffa16a15ffd14bcf5a610534e2e7cc0abea4b9ba2fd1e20e586a624c839c5b 46.159630357000 697649 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": 339158, "vin": [ { "gen": { "height": 339148 } } ], "vout": [ { "amount": 46159630357, "target": { "key": "bdffa16a15ffd14bcf5a610534e2e7cc0abea4b9ba2fd1e20e586a624c839c5b" } } ], "extra": [ 1, 119, 248, 181, 53, 151, 116, 42, 146, 113, 23, 209, 101, 106, 10, 17, 138, 171, 140, 196, 183, 162, 226, 154, 135, 203, 62, 46, 113, 175, 187, 114, 198, 2, 17, 0, 0, 0, 2, 84, 16, 149, 139, 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