Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e4fcc604ea60c7ab7038ac1f2f9041d25d6d3db8d4a8a010cb60a0db41ceeda

Tx prefix hash: 1184ee007b1cbf91f7a01e86fc94fe4daa56b10e8d779b7b61b129d70674bbbd
Tx public key: 177779ace38c3241c27e3f6d9c6257bab5eb28d437a0c710a95e81f4c56d0e62
Timestamp: 1730027279 Timestamp [UCT]: 2024-10-27 11:07:59 Age [y:d:h:m:s]: 00:027:16:20:27
Block: 1140651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19767 RingCT/type: yes/0
Extra: 01177779ace38c3241c27e3f6d9c6257bab5eb28d437a0c710a95e81f4c56d0e62021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7271f0f3ec9e5f3bbb101121ac28e82ead71243d922378c77aeef1fe3af7049a 0.600000000000 1624452 of 15

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": 1140661, "vin": [ { "gen": { "height": 1140651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7271f0f3ec9e5f3bbb101121ac28e82ead71243d922378c77aeef1fe3af7049a" } } ], "extra": [ 1, 23, 119, 121, 172, 227, 140, 50, 65, 194, 126, 63, 109, 156, 98, 87, 186, 181, 235, 40, 212, 55, 160, 199, 16, 169, 94, 129, 244, 197, 109, 14, 98, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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